Currency Exchange Rate API (SOAP)

(0 reviews)

Support and FAQ

Connecting to Development, Test, Stage, and Production Environments


To request access to the appropriate environment (Test, Stage, or Production), please submit your request. Once submitted, the API Owner will validate and grant access.

You will receive an email containing the access URL and your API credentials.

When making a request, please ensure that the client ID and client secret are included as part of the basic authentication in the header parameters :-

  • client_id
  • client_secret

The Client SSL certificate must also be provided (for Cloud APIs).

For Aspire APIs DEV Access will not be granted

How do I report bugs or production incidents?


An incident should be raised if there are any production incidents with the API. Incidents should be raised through Service Now which will subsequently be triaged by the MuleSoft support team.

Please find the steps to complete this here: https://rochewiki.roche.com/confluence/display/APIGOV/How+to+create+an+Incident

How do I request for more information?


Check out our FAQ page first! If you donโ€™t find the answer in our FAQ or gSite, you can raise any questions via our form โ€œRaise a questionโ€. Please contact the API owner or Architect only in case of escalations.

A request should be raised in Service Now for any request for information or to change/update deployment configuration. These requests are sent to the MuleSoft support team.

Please find the steps to complete this here: https://rochewiki.roche.com/confluence/display/APIGOV/How+to+Create+a+Request

How do I request new features?


New API project feature(s) or API project change request should be raised by creating a new JIRA requirement. This requirement will be sent to corresponding Agile Release Train Product Owner who will review and engage the architecture team.

Please find the steps to complete this here: Master Data Dashboard

Contacts


RoleNameRole DescriptionContact
API OwnerXavier GutierrezThe API Owner is the primary person who is responsible for prioritizing the feature backlog as well as determining if approval can be granted to any new consumer. The API Owner is accountable for the SLAs, Exchange content detail and accuracy of their API in MuleSoft Exchange. API Owner also is the one who can onboard consumers. The API Owner should be contacted if formal channels of intake such as Workday,ServiceNow is not yielding timely resultsxavier.gutierrez@roche.com
API ArchitectGagan ShindeAPI Architect is the primary person responsible for the APIโ€™s Architecture and Design. Other Solution Architects and Solution Engineers who are looking forward to reusing this asset may reach out to API Architect address any technical questions they have in case the documentation of each of the end points published in exchange via RAML is not self explanatory.gagan.shinde@roche.com

Reviews